home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
PROGRAM
/
TP060792.ARJ
/
06-07-92.TPC
Wrap
Text File
|
1992-06-07
|
42KB
|
1,195 lines
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 01-01-00 00:00:00
From
To
Subject
--- WM v2.01/92-0100
* Origin: A.C.E. of Spades (615)383-4381 The B.A.N. board (1:116/33)
* Tossed by SFToss v1.00b on 92/04/09 12:01:00
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 05-31-92 20:26:05
From Trevor Carlsen
To Mark Ouellet
Subject Abbreviations
SP> A list.. Welp, I M searching 4 1 4 about a year or so..
JM>> Not to be too annoying (TC? Don't slay me here), but
JM>>isn't the official language of this echo English?
DP> I talk Eng., these r abbriviations, makes the msg "Shorter"..
MO> Wrong, these make D messages "Harder" 2 read for us.
Mark I wouldn't let it worry you. If the language is pseudo English, the
message is on-topic and not against any of the rules, I ignore the stupidity
of such a practice. I certainly would never consider answering someone who
is so illiterate, or so lazy, to use such inanities. I don't believe anyone
of a reasonable level of intelligence would use this type of thing.
We will drop the subject.
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/05/31 15:39:55
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 05-31-92 13:47:29
From Mark Ouellet
To Jud Mccranie
Subject Re: Impact Of .Tpu Size O
On 27 May 92, you, Jud Mccranie, of 1:3645/10.0 wrote...
MO>> That's because the CRT INIT routine will reference
MO>> variables and procedures which are then kept by the linker.
MO>>
MO>> Remember using CRT installs video routines which
MO>> handle screen writes, those same routines you showed people
MO>> how to bypass to write ANSI screens.
JM> That wasn't me.
JM>
MO>> So naturely, anything used must be kept by the
MO>> linker but try using other routines such as WRITE and
MO>> WRITELN and GOTOXY etc... you'll see they were discarded
MO>> when you first compiled without using them.
Jud,
Allow me to refresh your memory ;-)
>Area : Pascal Intl 50000+ Received
>From : Mark Ouellet 23-May-92 22:15:56
>To : Jud Mccranie 23-May-92 22:15:56
>Subj.: Re: Impact Of .Tpu Size O
>
> On 18 May 92, you, Jud Mccranie, of 1:3645/10.0 wrote...
>
> GS>> If you RTFM, you'll see that it's "smart" linker throws out the
> GS>> code which isn't used.
>
> JM> Not so with the CRT unit. Just add it to USES and it will increase the
> JM> size of the EXE, even if you don't use anything in the CRT unit.
>
>Jud,
> That's because the CRT INIT routine will reference
>variables and procedures which are then kept by the linker.
>
> Remember using CRT installs video routines which
>handle screen writes, those same routines you showed people
>how to bypass to write ANSI screens.
>
> So naturely, anything used must be kept by the
>linker but try using other routines such as WRITE and
>WRITELN and GOTOXY etc... you'll see they were discarded
>when you first compiled without using them.
>
> Best regards,
> Mark Ouellet.
>
>--- ME2
> # Origin: One BEER gets me drunk.... usualy the 47th ;-) (Fidonet 1:240/1.4)
And if that ain't enough, I still have the original
message to which that reply was sent as well as the 50,000+
messages before that ;-)
Anyways, as you can plainly see you DID write that
message and my reply was intended to remind you that the CRT
initialized some constants and video related routines so the
smart linker can't ignore that.
Best regards,
Mark Ouellet.
--- ME2
* Origin: Buy ANY Seagate HD, get FREE Humidifier he he!!!(Fidonet 1:240/1.4)
* Tossed by SFToss v1.00b on 92/06/01 12:51:47
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 05-31-92 13:56:05
From Mark Ouellet
To Sean Ocker
Subject Re: SBlaster...
On 26 May 92, you, Sean Ocker, of 1117/369.0 wrote...
SO> Sorry I max out at 2400, but allow freqs from anyone at up to 4 hours.
Yes your BBS is a 2400 but isn't there a BBS using
9600 HST near you, one that doesn't cost you anything to
post there but that would still allow me to picj up the
stuff.
I would prefer FREQing the stuff. Much faster than
snail-mail. ;-)
SO> # Origin: While Parole_Board do begin num:=1117/369;
^^^^^^^^^^^
BTW Sean,
some mailers seem to have troubles with your adress,
IS IT 1117/369
or is it 1:117/369
I think the way it is noted in your origin line is the
problem.
Best regards,
Mark Ouellet.
--- ME2
* Origin: Buy ANY Seagate HD, get FREE Humidifier he he!!! (Fidonet 1:240/1.4)
* Tossed by SFToss v1.00b on 92/06/01 12:51:47
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 05-31-92 14:01:54
From Mark Ouellet
To Vince Laurent
Subject Re: Programming Adlib/Soundblaster [5/6]
On 26 May 92, you, Vince Laurent, of 1:382/10.0 wrote...
VL>>> I got 1,2, and 5 but where are 3,4, and 6?
|=>> Vince,
|=>> The original posting was missing 2,3 and 5, we only
|=>> got 1,4 & 6 so we now got #1 twice but are still missing #3.
|=>> So far we got 1, 2, 4, 5, 6. [Just in case I managed to lose
|=>> you in the first paragraph ;-) ]
VL> OK...so who ever gets a complete package first send it to the other, OK?
Vince,
Ok, when, if I get them before you I'll send them to
382/10.
Did you catch Lars's last post, he posted the whole
thing in 3 messages this time and they all made it here
without any problem, have you got them ??? If not I'll send
them to you.
Best regards,
Mark Ouellet.
--- ME2
* Origin: Buy ANY Seagate HD, get FREE Humidifier he he!!!(Fidonet 1:240/1.4)
* Tossed by SFToss v1.00b on 92/06/01 12:51:47
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 05-31-92 14:03:42
From Mark Ouellet
To Brad Roberts
Subject Re: SayGet Unit Test Program
On 25 May 92, you, Brad Roberts, of 1:382/52.0 wrote...
BR> Program TestSayGet;
BR>
BR> Uses
BR> Crt, SayGet;
BR> AddGet ('String :',SizeOf(Str1),10,15,15,GetString,LightGray,
BR> ReadGets;
BR> That is folks.. try it out.. its worked well for me, but then I'm not
BR> perfect. If you have any trouble or suggestions, let me know.
Some stuff deleted.
Brad,
IT looks great and BTW, forget that message about
missing #3-#8, they all made it this time around.
You used the exact approach I had in mind except I
wasn't fluent enough in OOP yet to build the project.
Very nice unit.
Best regards,
Mark Ouellet.
--- ME2
* Origin: Buy ANY Seagate HD, get FREE Humidifier he he!!! (Fidonet 1:240/1.4)
* Tossed by SFToss v1.00b on 92/06/01 12:51:47
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 05-31-92 23:35:09
From Mark Ouellet
To All
Subject Looking for SHAZAM (TV App. code gen.)
Hi All,
Since I got no answer last time I'm asking again.
I saw a file called SHAZAM on Turbo City which is
supposed to be a Turbo Vision application generator. I
assume it is like DLGDSN or MENUGEN.
Now I can't download or Freq from Turbo City so if
someone HAS SEEN or HAS this file available for Freq, from
unlisted nodes (Points) could you please tell me where to
get it.
I assume since Turbo City has it, someone else is
bound to have it also.
Best regards,
Mark Ouellet.
--- ME2
* Origin: Governments, Proof of Peter's principle (Fidonet 1:240/1.4)
* Tossed by SFToss v1.00b on 92/06/01 12:51:47
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-01-92 21:13:00
From Norbert Igl
To Max Maischein
Subject Detecting ANSI ? / INT 2Fh problems ??
>> BTW... won't even work with $2F this way, because Turbo's
>> INTR() has problems with the $2F function!
> Why, could you tell me more about this problem ??
> I've not used Intr a long time, especially since the BASM came out,
> but I'd like to know, what I'm missing !
Sorry, i screwed something up.....
There is no problem calling $2F with Intr(),
but there are *many* problems writing your own Int2F-Handler
without ASM/END or INLINE...
( STACK, [BP] and related things, you know?)
so i think, i get Off Topic discussing this DOS-behavior here.
Bye from Germany, Norbert
--- FD 2.02/FastEcho
* Origin: Let's talk about hex, baby.... (2:241/5300.3)
* Tossed by SFToss v1.00b on 92/06/02 13:37:27
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-01-92 01:01:07
From Mark Ouellet
To Stein-Ivar Johnsen
Subject Re: Looking for frequable SHAZAM
On 21 May 92, you, Stein-Ivar Johnsen, of 2:502/808.0 wrote...
MO>> I'm looking for this file SHAZAM which is a Turbo
MO>> Vision program generator.
MO>> If any one has this file up for Freq, from unlisted
MO>> nodes, please let me know.
SJ> You find it here as SHAZAM.ZIP 159750b
Stein-Ivar,
Thanks, I just sent another message about this and
this (God sent reply) was amongst the mail I picked up in
the process. Thanks again, I'm getting out of ME2 right
after this to Freq the file.
Best regards,
Mark Ouellet.
--- ME2
* Origin: Governements, Proof of Peter's principle (Fidonet 1:240/1.4)
* Tossed by SFToss v1.00b on 92/06/02 13:37:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-02-92 00:37:48
From Trevor Carlsen
To Jud Mccranie
Subject Reading records
JM> In TP, is there any good way to read records starting at a
JM> position in the file that is not a multiple of the record
JM> length?
I posted this on the 16th May. Seems you never got it.
{$I-}
function ReadRec(var f; { The typed or untyped file }
RecNo : longint;{ The record number to read ( zero based) }
Offset: word; { The size of the header }
var Rec;{ The record to be read - untyped for convenience }
ErrCode: { I/O error code } integer): boolean;
{ Reads a record number from a file of typed records that has an odd size}
{ header record. Returns true if read was OK. (Requires the DOS unit) }
var
OldSize,
result : word;
begin
with FileRec(f) do begin
OldSize := RecSize; { Save the declared record size }
RecSize := 1; { Change to a single byte record size }
seek(file(f),(RecNo * OldSize) + Offset);{ Seek to calculated offset }
RecSize := OldSize; { Restore the record size }
ErrCode := IOResult; { Check for I/O error }
if ErrCode <> 0 then { an I/O error occurred }
ReadRec := false
else { no I/O error } begin
BlockRead(file(f),Rec,1,result); { Read a single record }
ErrCode := IOResult; { Check for I/O error }
ReadRec := (ErrCode = 0) and (result = 1);
end; { else }
end; { with }
end; { ReadRec }
{$I+}
To use, just open your file as a typed file of the type you need then to read
record number RecordNumber -
if not ReadRec(f,RecordNumber,HeaderSize,YourRecord,ErrorCode) then
writeln('I/O read error ',ErrorCode,' record number ',RecordNumber);
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/02 19:32:07
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-02-92 00:40:42
From Trevor Carlsen
To All
Subject Rules of this echo
Would all sysops please ensure that a copy of these rules is available
to all users of the echo. It suggested that they be made a protected
message to ensure that normal message area housekeeping does not not
result in them being deleted.
RULES OF THE PASCAL ECHO
The Pascal echo is an internationally distributed FidoNet echo devoted
to the discussion and promotion of the Pascal programming language in
all its variations.
MODERATOR.
The currently appointed Moderator is Trevor Carlsen. He can be reached
by Netmail at 3:690/644 or by normal postage by writing to -
Trevor J Carlsen
Post Office Box 568
Port Hedland
Western Australia 6721
Phone (voice) +61 91 73-2026 (Local time is GMT+8)
(data) +61 91 73-2569
RULES.
1. Leave moderation to the moderator. Self appointed "echo policemen"
only waste echo space and create ill-feeling.
2. NO FLAMING. If you feel that you have been insulted in some way by
somebody, you have three options.
(a) Complain by netmail to the person concerned.
(b) Bring the matter to the moderator's notice - again by netmail.
(c) Ignore it. (the preferred option!)
3. Person-person messages that are not of general interest to other
users are STRICTLY not permitted. Netmail these types of messages.
4. When replying to messages try and do so "off-line" and quote some of
the message being replied to. However don't go overboard with
quoting. Quote just enough to enable the context of the reply to be
fully understood and in particular DO NOT INCLUDE PARTS OF THE TEAR
AND ORIGIN LINES.
5. When replying to questions with code examples, test them where
possible by compiling and running them (or state that you have not
done this). If possible always quote manual references, text
references etc. If your code example contains inline code then it is
only fair that you FULLY comment such code so that users can
determine the validity or viability of that code BEFORE risking it
on their own machines/data.
6. If replying to a question where you are disagreeing with the other
person's code or statement/s, support your viewpoint with working
code examples or valid text references. This will be more productive
than unsupported statements. If you are not prepared to do this then
don't reply in the first place!
7. Do not ENTER or REPLY TO off-topic messages.
The subject matter is Pascal. Discussions on religion, politics,
copyright, other programming languages and personal messages are
OFF-TOPIC. Any subject that is illegal or undesirable in a
responsible conference - eg discussion or tips on producing viruses or
how to illegally obtain access to information that the user is
unauthorised to obtain, is off-topic and will be severely dealt with.
Sometimes messages from other conferences become linked into another
conference due to faulty software. Replying to, or commenting on, such
messages is not permitted.
The main point is to use common sense. Some light hearted banter can
relieve the formality and brighten up ones day but do not carry this to
the length where it becomes an extended thread. The object of the echo
is to help, get help and enjoy communicating with like-minded people.
8. No "thank-you" or "no content" or "rubbish" messages. Sysops spend a
great deal of time and money to enable the distribution of echoes
such as this. Please respect this and avoid messages such as "Thank
you. Just what I needed" or "I agree" etc. By observing this
etiquette you will be helping to ensure greater participation in the
future.
9. All messages are to be in the English language and must be in PLAIN
TEXT. No encryption of any kind is permissable as this is in direct
contravention of FidoNet policy. This also means that binary file
transfer by conversion to asciiz is not allowed.
10. Limited, low key, on-topic advertising is permitted. The key words
here are ON-TOPIC and LOW KEY. Please restrict any notices to a
"one-time" issue and keep it brief and informative with NO SALES
HYPE. Any notice must be of interest to the echo participants in
general. Therefore this excludes such items as job vacancies, BBS
ads, for sale notices and similar as this is an International echo.
11. When seeking assistance -
a) If Turbo Pascal is your language, place the cursor on the key
word and call the on-line help (Ctrl-F1 in the IDE) to see if
the answer may be there.
b) Double check the manual to see if the answer is there.
c) When writing the message include enough code to allow would-be
helpers to have a chance to determine what the problem might be.
If possible condense the problem into a tiny working example and
post that.
d) This is a high volume echo so use a subject line in the message
that is likely to gain attention from the experts who are often
too busy to read every message. "Help wanted" or similar is a
good way to be ignored. Something like "Exec procedure not
working" is better.
e) Remember that a reply of "RTFM" is not considered or meant as an
insult. In fact it is considered a polite (in spite of the
connotations) way of reminding someone that the answer they seek
is in the manual.
f) Remember also that your reply may come from anyone, of possibly
unknown skill level. Don't be too upset if misled as it is
probably unintentional and will almost certainly be corrected by
another reader.
12. When offering advice or help -
a) Do so in a helpful, polite manner. Don't be condescending - not
everybody may have your experience or skills.
b) Refer to the page in the manual where the answer is if your
answer is "RTFM"!
13. Messages should comply with the FidoNet message requirements. Origin
lines should not exceed 79 characters, tear lines must not exceed 25
characters and messages should not contain any "hi-bit" (characters
with an ascii code over 127) characters. No encrypted text is
permitted. Messages are to be under 150 lines in length.
14. Election of Moderator. Under a normal situation, if the moderator
wishes to step aside, s/he will appoint a new moderator taking into
account the wishes of the regular users where possible. In the event
of a moderator ceasing to participate in the echo for a period of
three months without prior notice being given of the absence, for
whatever reason, then the ZEC (1:1/201) will conduct, or nominate a
regular and senior echo participant to conduct, an election for a new
moderator.
Any suggestions re alterations to this message are welcome. Please make
such suggestions by netmail.
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/02 19:32:07
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-02-92 00:45:27
From Trevor Carlsen
To John Meyers
Subject Telegard source code
JM> I too am interested in getting the Telegard 2.7 source.
JM> Anyone have it?
This has nothing to do with the topic of this conference. Please do not post
such a message again.
Trevor Carlsen
Moderator.
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/02 19:32:07
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-02-92 00:50:42
From Trevor Carlsen
To Jud Mccranie
Subject Re: Help - Reading Record
TC> Did you receive my solution?
JM> No, somehow I didn't. It seems that the best thing will be
JM> to open as a file of char (or byte), jump over the heading,
JM> and then blockread the size of the records, or a multiple of
JM> the records, then typecast the block as the record type.
That would not work. BlockRead only works on untyped files. However if the
file was untyped it would work. However there are better ways. BTW in the
above method why typecast? If the buffer a record of the appropriate type
(or an array of same in the case of the multiple read), no typecast is necessary
In another message I have re-entered my original solution for you.
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/02 19:32:07
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-03-92 14:32:10
From Dj Murdoch
To Paul Doerwald
Subject Re: Message base formats (was: overlay f
PD> Problem is that I'm complete C illiterate. I'll be taking
PD> a C high-school course in 2 years, but I really doubt
PD> until then that I'd be learning C. Is it well-documented
PD> enough that I could understand it?
I don't know. You'll have to take a look at it yourself.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:221/177.40)
* Tossed by SFToss v1.00b on 92/06/04 07:29:21
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-03-92 14:36:57
From Dj Murdoch
To Scott Samet
Subject Re: TBufStream allocs
SS> I'm curious where you find it documented that the heap
SS> will never exceed the value specified?
That's in the second indexed reference to $M in the Programmer's Guide - p.
211 in my book.
"The actual size of the heap depends on the minimum and maximum heap values,
which can be set with the $M compiler directive. Its size is guaranteed to
be at least the minimum heap size and never more than the maximum heap size."
SS> TP just plugs the $M values into the appropriate fields of
SS> the EXE file header. Right off the bat, it's rounded into
SS> paragraphs, so unless you specify a multiple of 16,
SS> there's going to be some difference.
SS> It's up to DOS to actually allocate them memory, so
SS> perhaps it's rounding to some coarser increment than 16.
SS> TP could (but does not) also save the exact heap value in
SS> a private location and use when initializing the heap variables.
Yes, I think you've got it right. DOS (version 5 at least) allocates the
number of 512 byte pages minus the header size plus the number of extra paragrap
s specified in the .EXE header. It ignores the "size mod 512" field. The
surprising thing is that the leftover part of the last page doesn't go to
waste - TP seems to take it into account when it positions the stack.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:221/177.40)
* Tossed by SFToss v1.00b on 92/06/04 07:29:21
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-03-92 01:02:59
From Trevor Carlsen
To Shawn Osborn
Subject Re: Turbo 6
SO> Mark, I've noticed many messages to/from you concerning TP5.5 & 6.0. I
SO> take it that you have tried both so maybe you can offer me some
SO> advice. I just bought Paradox 3.5, and the engine. Right now I use
SO> TP5, but see that PD engine supports only TP5.5 & 6. My question is:
SO> Becuase I will be writing database applications and want to write some
SO> in Pascal linking then thru the engin, which (in your opinion) is the
SO> one I should look at purchasing...
You do not have the luxury of a choice. TP6 is the only version being sold
(unless some old stock is available somewhere).
TP6 is a very much superior compiler to TP5.5 in spite of opinions you may
read to the contrary (which rarely state that they are opinions AND that they
refer to the IDE and not the compiler). I do not believe that there is a
single feature of TP6 - the compiler - that is a step backwards from TP5.5
and I doubt that anyone will point one out to you and there are several BIG
improvements -
* BASM (a MAJOR addition)
* Extended syntax
* 286 code generation
* New heap management technique
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/04 19:05:17
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-04-92 02:06:53
From Trevor Carlsen
To Herb Brown
Subject Wiping Disks
HB> Would it be safe to assume that all one needed to do to wipe
HB> the unused portion of a given disk by simply opening a file
HB> and writing to it till the disk was full then deleting that
HB> file?
I think you could safely make that assumption. One caveat might be to determine
what is the minimum allocation size on the disk and use that as the buffer
size for your writes.
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/04 19:05:17
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-03-92 18:21:16
From Dj Murdoch
To Dennis Menard
Subject Re: EXEC and ASSIGN
DM> When I issue the command:
DM> exec('c:\command.com', 'dothis');
DM> what results is a "Bad COMMAND search directory" error.
DM> What does this mean, and how can I correct it?
DM> COMMAND.COM exists where I have said it does.
The command being sent to command.com has to have a "/c" in front, or command.co
thinks you're specifying the directory to reload from. It's also a good
idea to use the COMSPEC environment variable rather than relying on finding
command.com in c:\. So, instead of your line, try:
exec(getenv('comspec'),'/c dothis');
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:221/177.40)
* Tossed by SFToss v1.00b on 92/06/05 14:22:39
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-03-92 18:24:17
From Dj Murdoch
To Herb Brown
Subject Re: Wiping Disks
HB> Would it be safe to assume that all one needed to do to
HB> wipe the unused portion of a given disk by simply opening
HB> a file and writing to it till the disk was full then
HB> deleting that file? I want to duplicate what Norton's
HB> wipeinfo program does, in a sense.
That'll get most of it, but you'll miss some things:
Filenames of erased files will still be sitting in the directories. If you
had subdirectories, they may be unnecessarily large; DOS grows them when you
add new files, but never shrinks them.
Tails of old files will still be there. If you have a few files on your disk,
the tails of those may contain old information, as well as the tail of the
one you're writing.
If the user has a cache that delays writes, it's conceivable that it would
be smart enough never to write your big file to disk at all - but that seems
pretty unlikely, since caches usually work at the BIOS level, not the DOS
level.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:221/177.40)
* Tossed by SFToss v1.00b on 92/06/05 14:22:39
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-04-92 05:58:13
From Dj Murdoch
To Jud Mccranie
Subject Re: Reading In Boot-Secto
DM> Yes, there weren't any serial numbers before 4.0. I don't know
DM> what sort of error you'd get if you called this service on an
DM> old version; it's probably safer to check the DOS version
DM> before you try.
JM> On the disks formated with 3.3 that I looked at, the area that later
JM> ---
That's all that made it out - could you try again? Thanks.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:221/177.40)
* Tossed by SFToss v1.00b on 92/06/05 14:22:39
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-04-92 06:21:13
From Dj Murdoch
To Jud Mccranie
Subject Re: Tp 6 Exe Slow?
JM> I tested two programs, one was
JM> non-recursive and the TP 6 EXE was faster. The other was recursive,
JM> and the TP 5.5 EXE was faster. I have just tested another recursive
JM> program, and the results were the same - the TP 5.5 EXE is about 10%
JM> faster than the 6.0 EXE, and G+ makes no measurable difference.
JM> So, it seems that recursion is much slower in TP 6.0. Can anyone
JM> shed any light on this?
I don't think it's recursion. The program below (a bad implementation of
a Fibonacci function) spends almost all of its time doing recursive calls,
and seems to be almost identical in execution speed in 5.5 or 6.0 with the
same compiler options (well, as close as I could get).
JM> Someone wanted to see my program that demoed the difference, and I
JM> can send a copy of this one on disk (the source is not that big, but
JM> it has a large data file with it). Or I can zip it up and let someone
JM> freq it or I can shorten the data file and get the source and data in
JM> about 5 or 6 messages, if someone wants to see it.
Try instead to distill out the pure elements of the program. For example,
the program below spends a ton of time on recursive calls, and doesn't show
the difference. If you can hit on whatever it is that's faster in 5.5 than
6.0, and write a program that does nothing else, you should get a clear demonstr
tion.
BTW, as people have said, the TP 6.0 .EXE file is bigger than the TP 5.5 .EXE:
3940 bytes versus 3843. It's mostly because the included part of the SYSTEM
unit is bigger; I'm not sure what has changed. The other differences are
that the Fib function is one byte smaller in 6.0 and the main body is a few
bytes bigger, because it does a stack check at the beginning.
{$A+,B-,D+,E+,F-,I+,L+,N-,O-,R-,S+,V+}
{$M 16384,0,655360}
function fib(i:integer):integer;
begin
case i of
0,1 : fib := i;
else fib := fib(i-2) + fib(i-1);
end;
end;
var
i : integer;
begin
for i:=1 to 30 do
writeln(i:5,fib(i):8);
end.
This takes 25 seconds to execute, on a 486-33 under Desqview as the only active
window.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:221/177.40)
* Tossed by SFToss v1.00b on 92/06/05 14:22:39
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-05-92 01:14:24
From Trevor Carlsen
To Alvin Lee
Subject Searching for a certain string in text f
AL> I was just wondering how to search for specific strings in a
AL> text file. I've heard that you use the function POS, but I
AL> would like an example of how you would use it. Anyone
AL> know?? Thanx in advance.
Providing no line exceeds 255 characters and that the specific string cannot
span lines here is a solution.
function Search(var f: text; SearchStr: string): integer;
{ Returns the line number in the file that the Search string is found }
{ in. If not found returns zero. If I/O error occurs returns a minus}
{ value which coresponds to the line number where the I/O error was. }
var
found,
IOErrror : boolean;
st : string;
line : integer;
begin
line := 0;
found := false;
IOError := false;
while (not found) and (not IOError) and (not eof(f)) do begin
{$I-} readln(f,st); {$I+}
IOError := IOResult <> 0;
inc(line);
found := pos(SearchStr,st) <> 0;
end;
if IOError then
Search := 0 - line
else
Search := line * ord(found);
end;
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/05 14:22:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-05-92 01:29:02
From Trevor Carlsen
To Jud Mccranie
Subject Tp 6 Exe Slow?
JM> Someone wanted to see my program that demoed the difference,
JM> and I can send a copy of this one on disk (the source is not
JM> that big, but it has a large data file with it). Or I can
JM> zip it up and let someone freq it or I can shorten the data
JM> file...
Shorten the data, Zip it, name it, tell me where to get it and what its name is.
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/05 14:22:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-05-92 17:47:00
From Norbert Igl
To Gerald Gutierrez
Subject Hex<>Dec
>> Thanks for the help. Does that code convert back to decimal too? Or
>> just from decimal to hex?
> I've never had the need to convert hex back into decimal .. sorry. 8)
> I don't expect it to be too difficult however. Basic procedure would
Hi...[BIG GRIN]...if anything else fails, read the manual... =(;-)
Var
HexStr : String;
DecVal : LongInt;
NumErr : Integer;
begin
HexStr := 'FFFF';
Val('$'+HexStr, DecVal, NumErr );
Writeln(' VAL() converted : $',HexStr,' to dec : ', DecVal );
end.
Bye from Germany, Norbert
--- FD 2.02/FastEcho
* Origin: STOP READING! You're leaving the MSG-sector (2:241/5300.3)
* Tossed by SFToss v1.00b on 92/06/06 07:53:23
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-06-92 08:41:27
From Trevor Carlsen
To Chris Kelling
Subject Re: A few Questions...
CK> The main difference between the two is the way the memory is
CK> used. The Stack is a first in last out (FILO), or the first
CK> element is going to end up being the last element used.
This is correct but I prefer to look at it as LIFO as that seems to make it
easier to understand.
CK> The Heap is just the oppisite. It is First in First out
CK> (FIFO). This is where your program stores the statements,
CK> where as the Stack is where the variable vaules (among other
CK> things like pointers for program control) are stored.
And this is just plain wrong! The heap is all of that memory allocated to
the program by DOS but not allocated for code, data or stack. The heap is
used to dynamically store information and can be allocated/deallocated in
any order at all. The heap manager controls the allocation of heap resources
on a "First Fit" basis. The programmer also has the ability to allocate heap
space as s/he sees fit.
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/06 13:09:53
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-06-92 09:42:18
From Trevor Carlsen
To Gerald Gutierrez
Subject Mod Struct [1/2]
GG> Protracker 1.1B Song/Module Format:
For some time now we have seen the number of messages on the technical aspects
of the SoundBlaster and various video systems and with no direct relationship
to Pascal becoming more frequent. I have ignored them in the hope that they
would go away.
This latest couple of messages are the straw that broke the camel's back :-)
In future all messages re the SB, MOD files, video technicals etc that are
not of GENERAL interest and have no DIRECT Pascal link are to be regarded
as off-topic in this echo.
Trevor Carlsen
Moderator.
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/06 13:09:53
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-06-92 17:46:25
From Trevor Carlsen
To Jud Mccranie
Subject Re: Topics..
JM> Pascal Lessons is for beginners and this one is for more advanced
JM> programmers. General, basic questions should be asked on "lessons".
This is precisely the impression I like to avoid giving. This echo is for
ALL levels of Pascal discussion.
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/06 13:09:53
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-06-92 11:21:39
From Trevor Carlsen
To Jud Mccranie
Subject Re: Why I Like Tp 5.5 Ide
PF> Could you please list some for me, I'm using 6.0 and my
PF> interest lies in being able to offer stable applications to my
PF> clients. If 6.0 has some flaws, I want to know what they are
PF> and the workarounds !
JM> ... The problems are with the 6.0 IDE. It is very hard to
JM> use, especially changing the search and replace/find
JM> options, for instance. The menu isn't sticky where it should
JM> be. The IDE is slow on a 386 with 8 megs of RAM and a fast
JM> HD. (50 MHz 486 may be fast enough.) There are anoying
JM> flashes on the screen when changing from one thing to
JM> another. Some nice features in 5.x are missing in 6.0 IDE.
JM> Keys don't work the way they should in the 6.0 IDE. All in
JM> all, the 6.0 IDE is very frustrating to use (if you are used
JM> to a good IDE like 4.0 - 5.5).
Jud, you do yourself absolutely no justice by continuing to harp on about
your pet hate (the TP6 IDE) in this way. By all means express your opinion
to those who ask, but stress that it is an opinion and not necessarily fact.
There are a big majority out there who would disagree with you and others
who would only partly agree.
*IMHO*, for a "professional" programmer to describe the TP4/5 IDEs as "good"
is very close to being a joke. They just don't come even close. They are
easier to use than the TP6 IDE (at first) but much less powerful.
*IMHO* the TP6 IDE is very much closer to being a professional grade environment
than are its predecessors but still has some considerable way to go yet.
It is extraordinarily hard to use in some areas and is nowhere near as intuitive
as the TP5 IDE. It also takes a long time to set up so that it works the way
you want it to. I suspect that this may be your real complaint. There are
many better, far more productive environments available on the market.
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/06 13:09:53
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 06-06-92 09:20:06
From Trevor Carlsen
To Peter Beeftink
Subject Writing directly to disk sectors.
PB> Would anyone know how to write a function which:
PB> 1) finds the disk sectors occupied by a file?
PB> 2) read/write to absolute disk sectors?
PB> The idea is to be capable of writing some bytes in the slack
PB> space of a file which is not included when the file is
PB> copied to another location.
I am always reluctant to post code here that will do direct sector writes.
I take the view that if you need that badly enough and don't have the necessary
skills or experience then you can purchase a professional library that will
include that capbility (Object or Turbo Professional). So that is what I
would recommend to you.
However in this case the problem as stated can easily be solved without resortin
to direct sector read/writes.
Open the file as untyped, save the length, seek to eof, write your information
to the end, and close the file. Reopen it, and truncate it to the old length.
The information written will still be there on the disk in the slack space.
To read that information, open the file, write a byte to an offset past the
extra information and then seek back and read the information. Close, reopen
and truncate to restore things back again.
TeeCee
--- TC-ED v2.01
* Origin: The Pilbara's Pascal Centre (+61 91 732930) (3:690/644)
* Tossed by SFToss v1.00b on 92/06/06 13:09:53